Clarify app submission requirements and packaging formats#5894
Clarify app submission requirements and packaging formats#5894joaodellarmelina wants to merge 1 commit intoMicrosoftDocs:docsfrom
Conversation
Updated submission guidelines to clarify supported packaging formats and benefits of MSIX. Removed references to traditional EXE/MSI installers for direct submission.
|
Learn Build status updates of commit 4812125: ✅ Validation status: passed
For more details, please refer to the build report. |
|
@microsoft-github-policy-service agree |
|
@joaodellarmelina : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
bot
added
apps/subsvc
Change sent to author
windows-app-sdk/svc
labels
|
@joaodellarmelina : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
There was a problem hiding this comment.
Pull request overview
Updates the “Submit your app to Microsoft Store” FAQ to clarify which packaging formats are supported for Store submissions and to highlight MSIX advantages, aligning the guidance with a more package-based submission flow.
Changes:
- Removes EXE/MSI references from the “reserve a name” and “packages” steps in the Partner Center submission overview.
- Rewrites the FAQ answer to list supported package file formats (MSIX/APPX family, XAP) and describe MSIX benefits.
- Adds explicit guidance stating EXE/MSI installers aren’t supported for direct submission and recommends converting to MSIX or related formats.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| To reserve a name: | ||
| - Go to your Apps & games section in Partner Center and select “New product.” | ||
| - Choose the type of app (e.g., MSIX/PWA or EXE/MSI). | ||
| - Choose the type of app (e.g., MSIX/PWA). |
There was a problem hiding this comment.
The instructions here imply only MSIX/PWA can be selected when creating a new product. Elsewhere in this repo there is current guidance for creating an “EXE or MSI app” in Partner Center (for example, hub/apps/publish/publish-your-app/msi/reserve-your-apps-name.md). Please either scope this FAQ explicitly to MSIX/PWA submissions or keep/restore the EXE/MSI option to avoid contradicting the rest of the documentation set.
| - Choose the type of app (e.g., MSIX/PWA). | |
| - Choose the appropriate product type for your app (for example, MSIX/PWA or EXE/MSI app). |
| - **Properties**: Set category and capabilities. | ||
| - **Age Ratings**: Complete content questionnaire for regional ratings. | ||
| - **Packages**: Upload your MSIX or EXE/MSI packages. | ||
| - **Packages**: Upload your MSIX package. |
There was a problem hiding this comment.
This step narrows package upload to “your MSIX package”, but other Microsoft Store docs in this repo indicate multiple Windows package formats are accepted for MSIX submissions (e.g., .msixupload/.appxupload/.appxbundle). Consider rewording to “upload your package(s)” or explicitly listing the supported formats to avoid giving incorrect requirements.
| - **Packages**: Upload your MSIX package. | |
| - **Packages**: Upload your package(s), such as supported MSIX and related package formats. |
| The Microsoft Store requires apps to be submitted using supported packaging formats such as MSIX and related package types. | ||
|
|
||
| **MSIX Benefits are**: | ||
| **Supported package formats include**: | ||
| - .msix | ||
| - .msixbundle | ||
| - .msixupload | ||
| - .appx | ||
| - .appxbundle | ||
| - .appxupload | ||
| - .xap | ||
|
|
||
| **MSIX benefits include**: | ||
| - Free Microsoft code signing and CDN hosting. | ||
| - Easier updates, better integration with Windows features. | ||
| - Enables advanced capabilities like flighting and commerce. | ||
|
|
||
| **MSI/EXE Submission**: | ||
| - Allowed since June 2021. | ||
| - You must provide a URL or upload the installer in submission. | ||
| - Requirements: | ||
| - Must be .exe or .msi only. | ||
| - Offline installer – no downloads during setup. | ||
| - Installer must not change after submission or bundle unrelated software. | ||
|
|
||
| Both app types can be submitted in Store depending on developer's needs. | ||
| - Easier updates and better integration with Windows features. | ||
| - Support for advanced capabilities like flighting and commerce. | ||
|
|
||
| **EXE/MSI installers**: | ||
| - Traditional installer formats such as .exe or .msi are not supported for direct submission in the Microsoft Store. | ||
| - Developers should convert or package their applications using MSIX or one of the supported formats listed above to ensure compatibility with Store requirements and certification processes. |
There was a problem hiding this comment.
The answer states that “traditional installer formats such as .exe or .msi are not supported for direct submission”, but this repo contains a full MSI/EXE submission guide that describes reserving an “EXE or MSI app” and uploading EXE/MSI packages in Partner Center (see hub/apps/publish/publish-your-app/msi/create-app-submission.md and .../msi/upload-app-packages.md). Please reconcile these docs—either qualify this FAQ as “for MSIX apps”, or update/remove the MSI/EXE guide and adjust wording here so the documentation set is internally consistent.
| - Traditional installer formats such as .exe or .msi are not supported for direct submission in the Microsoft Store. | ||
| - Developers should convert or package their applications using MSIX or one of the supported formats listed above to ensure compatibility with Store requirements and certification processes. | ||
|
|
||
| Using msix package format ensures a more reliable, secure, and streamlined installation and update experience for users. |
There was a problem hiding this comment.
“Using msix package format” should use the product name capitalization (“MSIX”) and read more clearly as “Using the MSIX package format …”. This helps keep terminology consistent across the docs.
| Using msix package format ensures a more reliable, secure, and streamlined installation and update experience for users. | |
| Using the MSIX package format ensures a more reliable, secure, and streamlined installation and update experience for users. |
Updated submission guidelines to clarify supported packaging formats and benefits of MSIX. Removed references to traditional EXE/MSI installers for direct submission.